System and method for incremental object tracking and progressive remittance

ABSTRACT

A shipping remittance processor may receive periodic checkpoint data packets during shipping of an object, via a handler, along a shipping route. The shipping remittance processor may then analyze tracking information located in the checkpoint data packet to determine if the tracking information is authentic, and if the object has reached a checkpoint along the shipping route. If the object has reached the checkpoint, the shipping remittance processor may output a remittance indication indicating to output a portion of the total delivery remittance to the handler&#39;s remittance account.

BACKGROUND

Handlers, or shipping couriers, typically pick up an object for shippingand get paid upon completed shipment of said object. This antiquatedsystem of shipping is burdensome on handlers who are travelling longdistances. For example, many handlers must front shipping costs untilthe shipment is made.

SUMMARY

A shipping remittance processor may receive periodic checkpoint datapackets during shipping of an object, via a handler, along a shippingroute. The shipping remittance processor may then analyze trackinginformation located in the checkpoint data packet to determine if thetracking information is authentic, and if the object has reached acheckpoint along the shipping route. If the object has reached thecheckpoint, the shipping remittance processor may output a remittanceindication indicating that a portion of the total delivery remittancethat the handler would otherwise be due for delivering the object to itsfinal destination should be sent to the handler's remittance account.Thus, the handler receives incremental remuneration as he or she reachescheckpoints along the shipping route.

In an aspect, embodiments of a computer-implemented method forincremental object tracking and progressive remittance are described.Embodiments of the method may comprise receiving, at a shippingremittance processor, a checkpoint data packet including trackinginformation of an object during shipment along a shipment route.Embodiments of the method may also comprise determining, via theshipping remittance processor, that the object has reached a checkpointalong the shipment route, the checkpoint being located between abeginning and end of the shipment route. The method may, upondetermining that the object has reached the checkpoint, output aremittance indication indicating that a portion of a total deliveryremittance is to be distributed to a handler account.

In another aspect, embodiments of a system for incremental objecttracking and progressive remittance are disclosed. Embodiments of thesystem may comprise a memory storing a checkpoint schedule definingcheckpoints for an object traveling along a shipping route. Embodimentsof the system may also comprise a shipping remittance processor adaptedto execute non-transitory computer readable instructions to: receive acheckpoint data packet including tracking information of the objectduring shipment along the shipment route, compare the trackinginformation with the checkpoint schedule to determine if the object hasreached one of the checkpoints, and output a remittance indicationindicating that a portion of a total delivery remittance is to bedistributed to a handler account.

In yet another aspect, embodiments of a handler device for incrementalobject tracking and progressive remittance are disclosed. Embodiments ofthe handler device may comprise a memory storing a checkpoint scheduleidentifying shipping checkpoints along a shipping route for shipping anobject. Embodiments of the handler device may also comprise a trackerfor determining a real-time geographical location of the handler device.Embodiments of the handler device may also comprise a handler processorin communication with the memory and tracker, the processor configuredto analyze the checkpoint schedule and output, via an output device, aprompt to a user to obtain authentication information in response to thereal-time geographical location matching one of the checkpoints.Embodiments of the handler device may also comprise an input interfaceconfigured to receive the authentication information.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 depicts an exemplary system for incremental object tracking andprogressive remittance, in one embodiment.

FIG. 2 depicts a block diagram of the shipper information of FIG. 1 infurther detail in embodiments.

FIG. 3 depicts a block diagram of the shipment information of FIG. 1 infurther detail in embodiments.

FIG. 4 depicts a block diagram of the handler information of FIG. 1 infurther detail in embodiments.

FIG. 5 depicts a block diagram of the handler device of FIG. 1 infurther detail in embodiments.

FIG. 6 depicts an exemplary map showing a shipping route having a start,end, and a first checkpoint, second checkpoint, third checkpoint, andfourth checkpoint, in an embodiment.

FIG. 7 depicts an exemplary method for incremental object tracking andprogressive remittance, in embodiments.

DETAILED DESCRIPTION OF THE EMBODIMENTS

FIG. 1 depicts an exemplary system 100 for incremental object trackingand progressive remittance, in one embodiment. FIG. 2 depicts a blockdiagram 200 of shipper information 106 in further detail in embodiments.FIG. 3 depicts a block diagram 300 of shipment information 108 infurther detail in embodiments. FIG. 4 depicts a block diagram 400 ofhandler information 110 in further detail in embodiments. FIG. 5 depictsa block diagram 500 of handler device 124 in further detail inembodiments. FIGS. 1-5 are best viewed together with the followingdescription.

In embodiments, system 100 includes shipping remittance processor 102.In embodiments, shipping remittance processor 102 is located within ashipping company server 104. Shipping remittance processor 102 mayinclude one or more computers having one or more memory for storingshipper information 106, shipment information 108, and handlerinformation 110. Shipping remittance processor 102 may include hardware,firmware, software, or any combination thereof adapted to execute thefunctionality discussed below. In embodiments, shipping company server104 includes a single computer or multiple computers forming a servernetwork. Shipping remittance processor 102 from a component of any oneor more of the computers forming shipping company server 104.

In embodiments, shipping remittance processor 102 may be incommunication with a communication manager 112. By being incommunication with shipping remittance processor 102, communicationmanager 112 may be integral to shipping remittance processor 102, orseparate therefrom but nonetheless capable of transmitting data thereto.Communication manager 112 may include, but is not limited to, a wired orwireless receiver and a wired or wireless transceiver. Accordingly,shipping remittance processor 102 may be in communication with network114, for example via communication manager 112. Network 114 may be anyone or more of an Internet network, cellular network, WiFi network, orother network type.

Shipping remittance processor 102 may receive a checkpoint data packet116, via network 114. In embodiments, checkpoint data packet 116includes tracking information of one or more shipped objects 118 presentwithin handler shipping system 120. Checkpoint data packet 116 mayinclude information constituting one or more of shipper information 106,shipment information 108, or handler information 110. In embodiments,checkpoint data packet 116 includes tracking information of objects 118obtained during shipment of the object. However, shipping remittanceprocessor 102 may be accessed by shipper 140 and/or handler 122 at anytime pre-, during, or post-object shipment to view or modify one or moreof shipper information 106, shipment information 108 and handlerinformation 110. In embodiments, handler shipping system 120 includes ahandler 122 having an associated handler device 124, and atransportation vehicle 126 capable of transporting the object(s) 118.Handler 122 may operate transportation vehicle 126. Handler device 124may be one or more of a mobile device, smartphone, tablet, personalcomputer, or other device. Handler device 124 includes hardware capableof connecting wirelessly to network 114, such as a cellular module, WiFimodule, or other wireless communications module. Shipped objects 118 mayinclude one or more of: freight, transported vehicles, passengers on apassenger vehicle, or any other item being transported.

Checkpoint data packet 116 may be a wireless transmission that includestracking information from one or more of: first tracking tag 128associated with object 118, second tracking tag 130 mounted ontransportation vehicle 126, or handler device 124. Checkpoint datapacket 116 may be transmitted to shipping remittance processor 102 atone or more checkpoints along the shipping route.

In embodiments, first tracking tag 128 is located on each individualobject 118. In additional embodiments, first tracking tag 128 isassociated with a group of objects 118, such as on a freight pallet. Inyet additional embodiments, first tracking tag 128 is a device, such asa mobile device, smartphone, tablet, or personal computer of a passengerthat is travelling via transportation vehicle 126. In embodiments, firsttracking tag 128 includes a wireless transmission component capable oftransmitting tracking information 132 of object 118 (or group ofobjects) to network 114, which is then relayed to shipping remittanceprocessor 102 as all or a portion of checkpoint data packet 116. Inembodiments, first tracking tag 128 includes a wireless transmissioncomponent capable of transmitting tracking information 133 of object 118(or group of objects) to handler device 124, which in turn transmitstracking information 133 of objects 118 to network 114, which in turntransmits said tracking information 133 to shipping remittance processor102 as all or a portion of checkpoint data packet 116.

In embodiments where first tracking tag 128 transmits directly tonetwork 114, the data may automatically transmit without intervention byhandler device 124, thereby potentially providing more consistent andreliable transmission times. In embodiments utilizing handler device 124to relay tracking information 133, as opposed to directly transmittingtracking information 132 to network 114, power consumption by firsttracking tag 128 is significantly reduced. In such embodiments, thetransmission protocol for transmitting tracking information 133 may below energy, such as Bluetooth, or even zero power such as an optical orphysical scan of first tracking tag 128 by handler device 124. Automatictransmission of the data from first tracking tag 128 to handler device124 may be accomplished via first tracking tag 128 automaticallytransmitting tracking information 133 to handler device 124, or viahandler device 124 pinging first tracking tag 128, when a checkpoint isreached.

In embodiments, second tracking tag 130 is located on transportationvehicle 126. In embodiments, second tracking tag 130 includes a wirelesstransmission component capable of transmitting tracking information 134of transportation vehicle 126 to network 114, which is then relayed toshipping remittance processor 102 as all or a portion of checkpoint datapacket 116. In embodiments, second tracking tag 130 includes a wirelesstransmission component capable of transmitting tracking information 135of transportation vehicle 126 to handler device 124, which in turntransmits tracking information 135 transportation vehicle 126 to network114, which in turn transmits said tracking information 135 to shippingremittance processor 102 as all or a portion of checkpoint data packet116.

In embodiments where second tracking tag 130 transmits directly tonetwork 114, the data may automatically transmit without intervention byhandler device 124, thereby potentially providing more consistent andreliable transmission times. In embodiments utilizing handler device 124to relay tracking information 135, as opposed to directly transmittingtracking information 134 to network 114, power consumption by secondtracking tag 130 is significantly reduced. In such embodiments, thetransmission protocol for transmitting tracking information 135 may below energy, such as Bluetooth, or even zero power such as an optical orphysical scan of second tracking tag 130 by handler device 124.Automatic transmission of the data from second tracking tag 130 tohandler device 124 may be accomplished via second tracking tag 130automatically transmitting tracking information 135 to handler device124, or via handler device 124 pinging second tracking tag 130, when acheckpoint is reached.

The wireless transmission component of each of first tracking tag 128and second tracking tag 130 may respectively be one or more of aBluetooth device, WiFi device, cellular connectivity device, RFID tag orQR code that is scanned by handler device 124, or other wirelesstransmission system for transmitting tracking information to network 114and/or handler device 124.

In embodiments, handler device 124 transmits tracking information 136 ofhandler 122 to network 114, which in turn transmits said trackinginformation 136 to shipping remittance processor 102. As discussedabove, in embodiments, handler device 124 may serve as a relay devicefor transmitting one or more of tracking information 133 of object 118or tracking information 135 of transportation vehicle 126. In suchembodiments, tracking information 136 may include one or more of:handler tracking information 136, object tracking information 133,and/or transportation vehicle tracking information 135.

Thus, it should be understood that checkpoint data packet 116 mayinclude any one or more of: object tracking information 132 received bynetwork 114 from first tracking tag 128, object tracking information 133relayed to network 114 from first tracking tag 128 via handler device124, transportation vehicle tracking information 134 received by network114 from second tracking tag 130, transportation vehicle trackinginformation 135 relayed to network 114 from second tracking tag 130 viahandler device 124, and handler tracking information 136 received bynetwork 114 from handler device 124.

Shipping remittance processor 102 may further be in communication, vianetwork 114, with one or more of: a shipper device 138 associated with ashipper 140 (who, e.g., requests that the handler 122 deliver one ormore of objects 118), a shipper remittance account 142 having anassociated shipper remittance account identification (ID) number 144,and a handler remittance account 146 having an associated handlerremittance account ID number 148. Shipper 140 may desire to ship one ormore of objects 118, and may access shipping remittance processor 102via interaction with shipper device 138 to configure shipment details asdiscussed in further detail below. Shipper device 138 may be one or moreof a mobile device, smartphone, tablet, personal computer, or otherdevice in communication with network 114.

Upon receipt of checkpoint data packet 116, shipping remittanceprocessor 102 may analyze one or more of shipper information 106,shipment information 108 and handler information 110 to determinewhether a remittance indication 150 is to be output to shipperremittance account 142. Accordingly, in embodiments, multiple remittanceindications 150 may be output as object 118 travels along the shippingroute. When remittance indication 150 is output, a remittance istransferred from shipper remittance account 142 to handler remittanceaccount 146. In embodiments, shipper remittance account 142 may be afinancial institution, such as a creditor, bank, etc. In otherembodiments, shipper remittance account 142 is a balance held by theshipping company managing one or more of shipping company server 104 orshipping remittance processor 102, and such balance is preloaded byshipper 140 with a desired balance upon configuration of shipperinformation 106. In embodiments, handler remittance account 146 may be afinancial institution, such as bank, creditor, etc. In embodiments,handler remittance account 146 may be a prepaid resource in which uponreceiving remittance indication 150, shipper remittance account 142loads an additional remittance value onto the prepaid card.

As shown in FIG. 2, shipper information 106 includes details aboutshipper 140. Shipper information 106 may be stored within transitory ornon-transitory memory associated with shipping remittance processor 102and/or shipping company server 104 such that it is accessible viashipping remittance processor 102 and/or network 114. Shipper 140 mayaccess shipping remittance processor 102 via interaction with shipperdevice 138 and network 114, to configure shipper information 106. Inembodiments, shipper information 106 includes one or more of shipperidentification 202, shipper remittance account information 204, objectshipment details 206, and shipping statistics 208. Shipperidentification 202 may include identifying information of shipper 140such as the shipper's name, address, contact information, etc.

Shipper remittance account information 204 may include information ofshipper remittance account 142 such as shipper remittance account IDnumber 144, routing information, institution name, etc.

Object shipping details 206 may include information about an object(e.g. one or more of objects 188) for shipment. For example, objectshipping details 206 may identify the objects for shipment 210, theobject remittance details 212, and the checkpoints due 214. Objectremittance details 212 may include the total remittance which is to bepaid for each object 118 identified within objects for shipment 210, aswell as a remittance value per object checkpoint as indicated within thecheckpoints due 214 information. Checkpoints due 214 may include detailsregarding the checkpoints that the handler 122 must meet during ashipping route in order to receive the object remittance prescribed byobject remittance details 212. In certain embodiments, checkpoints due214 indicates an amount of objects 118, of the total objects, that areto be dropped off at the checkpoint. For example, if handler 122 isshipping a batch of objects 118 and certain of those are to be droppedoff at each or some of the checkpoints, checkpoints due 214 may indicatenot only those specific checkpoints that must be made, but also whichobjects 118 need to be left at the checkpoint.

In certain embodiments, the object shipping details 206 may defineaspects of the handler 122. For example, where the handler 122 is atravelling salesperson, shipper 140 may be an employer of handler 122.In such a situation, object shipping details 206 may provide details ofhandler 122 such that as handler 122 travels along a sales trip route(aka shipping route), the handler 122 is given per diem payment for foodand lodging, or other expenses.

Shipping statistics 208 may include information about previous shipmentsmade by shipper 140, including remittance information, shipper reviews,percent of successful remittances, etc.

In embodiments, the object 118 and shipper 140 may be the same. In otherwords, the shipper 140 may be travelling via transportation vehicle 126.In such embodiments, the object shipment details 206 may include ticketinformation such that object remittance details 212 identifies an amountfor such travel based upon each stop along the travel route.

As shown in FIG. 3, shipment information 108 may include informationspecific to objects 118 that are being shipped. Shipment information 108may be stored within transitory or non-transitory memory associated withshipping remittance processor 102 and/or shipping company server 104such that it is accessible via shipping remittance processor 102 and/ornetwork 114. In embodiments, shipment information 108 may include one ormore of: object description 302, tracking tag information 304, objectshipping requirements 306, and object shipment details 308.

Object description 302 may define object characteristics such as thetype of object, weight of object, size of object, etc.

Tracking tag information 304 may define a tracking tag associated withthe object being shipped. In embodiments, tracking tag information 304is defined via handler 122 interacting with handler device 124 tocommunicate with shipping remittance processor 102 via network 114 andidentify identification information of one or more of handler device124, first tracking tag 128 and second tracking tag 130 as tracking taginformation 304. In embodiments, tracking tag information 304 is definedvia shipper 140 interacting with shipper device 138 to communicate withshipping remittance processor 102 via network 114 and identifyidentification information of first tracking tag 128 associated withobject 118. During setup and configuration of tracking tag information304, handler 122 need not specifically be the courier that istransporting objects 118, but may be another entity or person assistingin the preparation of object 118 for shipment.

Object shipping requirements 306 may identify information requiredduring shipment of the object. In embodiments, object shippingrequirements includes one or more of checkpoint schedule 310 andcheckpoint remittance 312. Checkpoint schedule 310 may be similar tocheckpoints due 214 as discussed above with respect to FIG. 2.Checkpoint remittance 312 may include information similar to objectremittance details 212 discussed above with respect to FIG. 2.

Object shipment details 308 may include information included incheckpoint data packet 116 that is received by shipping remittanceprocessor 102 during shipment of object 118. In embodiments, objectshipping details 308 includes information about one or more of: thecheckpoints reached 314 by the shipped object during shipment, thecheckpoints missed 316 by the shipped object during shipment, and theremittance details 318 associated with the object during shipment.

Checkpoints reached 314 may include a list of each checkpoint, asindicated within checkpoint schedule 310 and/or checkpoints due 214,that has been reached by object 118 along shipping route. For example,shipping remittance processor 102 may compare one or more of trackinginformation 132, 133, 134, 135, 136 discussed above, with one or more ofcheckpoint schedule 310 and/or checkpoints due 214, to determine ifobject 118 has reached the appropriate checkpoint. If the object hasreached the appropriate checkpoint, such status may be indicated withincheckpoints reached 314.

Checkpoints missed 316 may include a list of each checkpoint, asindicated within checkpoint schedule 310 and/or checkpoints due 214,that has been missed by object 118 along shipping route. For example,shipping remittance processor 102 may compare one or more of trackinginformation 132, 133, 134, 135, 136 discussed above, with one or more ofcheckpoint schedule 310 and/or checkpoints due 214, to determine ifobject 118 did not reached the appropriate checkpoint. If the object didnot reach the appropriate checkpoint, such status may be indicatedwithin checkpoints missed 316.

Remittance details 318 may identify what remittances have been made tothe handler remittance account 146 based upon checkpoints reached 314.For example, when the object 118 reaches a checkpoint, as discussed infurther detail below, the shipping remittance processor 102 may output aremittance indication 150 (see FIG. 1) indicating for the shipperremittance account 142 to release remittance to handler remittanceaccount 146. Upon output of said remittance indication 150, shippingremittance processor 102 may indicate a record thereof in remittancedetails 318. Accordingly, in embodiments, multiple remittanceindications 150 may be output as object 118 travels along the shippingroute.

As shown in FIG. 4, in embodiments, handler information 110 may includeinformation via handler 122. Handler information 110 may be storedwithin transitory or non-transitory memory associated with shippingremittance processor 102 and/or shipping company server 104 such that itis accessible via shipping remittance processor 102 and/or network 114.In embodiments, handler information 110 may include one or more of:handler ID information 402, handler remittance account information 404,handler shipment details 406, and handler statistics 408.

Handler ID information 402 may include identification information ofhandler 122. In embodiments, handler ID information includes one or moreof: handler contact information 410 and handler authenticationinformation 412. Handler contact information 410 may include address,phone number, etc. Handler authentication information 412 may includeone or more of a template indicating a fingerprint scan, retinal scan,or facial scan of handler 122, and an authentication token associatedwith handler device 124 such as a SIM card ID.

Handler remittance account information 404 may include informationregarding the remittance account 146 of handler 122. In embodiments,handler remittance account information 404 includes one or more ofremittance account ID 414, remittance balance 416, and receiptinformation 418. Remittance account ID 414 may include routinginformation, institution name, etc. of the handler remittance account146. Remittance balance 416 may include the balance paid to handlerremittance account 146. Remittance receipt information 418 may includetransaction details regarding remittance account 146.

Handler shipment details 406 includes details regarding variousshipments performed, to be performed, or being performed by handler 122.In embodiments, handler shipment details 406 includes one or more of:handler geofence 419, objects accepted for shipment 420, checkpoints due422, checkpoints made 424, and object remittance details 426. Handlergeofence 419 may define a boundary that handler 122 is capable ofshipping within. For example, handler geofence 419 may identify thathandler 122 is only allowed, or willing, to ship objects within acertain state, county, city, etc. Accordingly, handler 122 is onlypresented objects 118 that meet these requirements. Objects accepted forshipment 420 may include one or more of: past objects accepted andalready shipped by handler 122, objects currently being shipped byhandler 122, and objects accepted by handler 122 to be shipped at afuture date. Checkpoints due 422 may include a list of each checkpointthat handler 122 is to meet during each object identified in objectsaccepted 420, including objects currently being shipped and objectsbeing shipped in the future by handler 122. Checkpoints made 424 mayinclude a list of each checkpoint that handler 122 has already metincluding each object currently being shipped and past objects shippedas identified in objects accepted 420.

FIG. 5 depicts a block diagram 500 of handler device 124 of FIG. 1, inembodiments. Handler device 124 may include one or more of: memory 502in communication with handler processor 504, receiver 506, transmitter508, an input interface 510, a tracker 512, and an output device 514.

Memory 502 may include transitory or non-transitory memory configured tostore one or more of: a checkpoint schedule 516, remittance information518, location information 520, authentication information 522, and aprompt 524.

In embodiments, checkpoint schedule 516 indicates each checkpoint thatthe handler 122 must meet while shipping a given object (e.g. object118) along a shipping route. Checkpoint schedule 516 may be transmittedto handler device 124 from shipping remittance processor 102 via network114 such that checkpoint schedule 516 is received by handler device 124via receiver 506.

In embodiments, remittance information 518 includes informationregarding remittance indication output by shipping remittance processor102. Remittance information 518 may include verification that remittancehas been made from shipper remittance account 142 to handler remittanceaccount 146. Remittance information 518 may be transmitted by shippingremittance processor 102 as a remittance packet via network 114 suchthat the remittance packet is received by handler device 124, viareceiver 506.

In embodiments, location information 520 includes tracking locationinformation about one or more of handler device 124, objects 118, andtransportation vehicle 126. For example, tracker 512 may monitor thelocation of handler device 124 and store the location within locationinformation. In embodiments, receiver 506 receives one or more oftracking information 133 of objects 118 (FIG. 1) and trackinginformation 135 of transportation vehicle 135 (FIG. 1), and the trackinginformation is then stored as location information 520. Locationinformation 520 may then be transmitted, via transmitter 508, toshipping remittance processor 102 via network 114, for example, withincheckpoint data packet 116. In embodiments, transmitter 508 may notalways have connectivity to network 114. In such embodiments, locationinformation 520 may be stored within memory 502 until transmitter 508obtains connectivity to network 114 at which time transmitter 508transmits tracking information 136, including location information 520to network 114.

In embodiments authentication information 522 is utilized toauthenticate handler device 124. For example, authentication information522 may include a token indicating verification of handler device 124.Such token may be an electronic token specific to the handler device 124such as a SIM card identifier, or another encryption key. In suchembodiments, interface 510 may receive such electronic token viainteraction with handler 122 or automatically via accessing theelectronic token stored within memory 502. In embodiments,authentication information 522 may include biometric information ofhandler 122 using handler device 124. For example, handler 122 mayinteract with input interface 510 to provide one or more of a biometricscan including: fingerprint scan of the handler 122, retinal scan of thehandler 122, facial scan of the handler 122 or other type of biometricscan. Authentication information 522 may then be transmitted, viatransmitter 508 to shipping remittance processor 102, for example,within checkpoint data packet 116. Authentication information 522 maythen authenticate location information 520 also sent within checkpointdata packet 116.

In embodiments, prompt 524 may be used to notify handler 122 of anupcoming, or arrived at, checkpoint. For example, prompt 524 may begenerated by handler processor 504 and output via output device 514 suchthat handler 122 knows to acquire location information 520. In certainembodiments, handler 122 may acquire location information 520automatically based upon tracker 512, and/or an automatic reception, viareceiver 506, of one or more of tracking information 133 from object 118and tracking information 135 from transportation vehicle 126.

Handler processor 504 may be a microprocessor, or other discrete digitalcircuitry, adapted to execute functionality of one or more of memory502, receiver 506, transmitter 508, input interface 510, tracker 512,and output device 514.

Receiver 506 may be a wireless receiver capable of communicating withnetwork 114. Transmitter may be a wireless transmitter capable ofcommunication with network 114. Receiver 506 and transmitter 508 may beindependent from one another or may be combined such as a transceiver.

Input interface 510 may be a device for interfacing with handler 122. Inembodiments, input interface 510 is a biometric scanner capable ofscanning one or more of: a fingerprint of the handler 122, a retinalscan of the handler 122, a facial scan of the handler 122, and anothertype of biometric scan of the handler 122.

Tracker 512 may be one or more of a GPS tracker, a WiFi enabled tracker,or a cellular module capable of tracking location via cellularconnectivity.

Output device 514 may be one or more of a visual, audio, or tactileoutput. For example, output device 514 may be a display of handlerdevice 124. In embodiments, output device 514 is an audio speaker ofhandler device 124. In embodiments, output device 514 is a vibrationsystem of handler device 124.

FIG. 6 depicts an exemplary map 600 showing shipping route 602 having astart 604, end, 606 and a first checkpoint 608, second checkpoint 610,third checkpoint 612, and fourth checkpoint 614, in an embodiment. Asshown, an object (e.g. object 118) is scheduled for shipment alongshipping route 602 with a start 604 in Stamford, Conn. In embodiments,to schedule the shipment, a shipper (e.g. shipper 140) utilizes ashipper device (e.g. shipper device 138) to configure one or both ofshipment information (e.g. shipment information 108) and shipperinformation (e.g. shipper information 106). During such configuration,the shipper may determine the start and end of the shipping route, aswell as the number and locations of each checkpoint along the route.Such information may be stored within a shipping remittance processor,such as object shipment details 206 (FIG. 2) and/or object shippingrequirements 306 (FIG. 3).

After configuration by the shipper, a handler may accept said objectsfor shipment, and begin shipping such objects. In one example ofembodiments, handler 122 may accept an object 118, and begin travellingalong shipping route 602 from start 604 to first checkpoint 608. Uponarrival at first checkpoint 608, a first checkpoint data packet may besent to the shipping remittance processor. In the example of FIG. 6,first checkpoint 608 is Chicago, Ill. For example, a first instance ofcheckpoint data packet 116 may be sent to shipping remittance processor102. Depending on the requirements determined by either shippingremittance processor 102 or shipper 140, first checkpoint data packetmay include one or more of: location information received directly froma tag associated with the shipped object (e.g. tracking information 132in FIG. 1), location information from a tag associated with the shippedobject that is relayed via a handler device (e.g. tracking information133 in FIG. 1), location information received directly from atransportation vehicle carrying the shipped object (e.g. trackinginformation 134 in FIG. 1), location information from a transportationvehicle carrying the shipped object that is relayed via a handler device(e.g. tracking information 135 in FIG. 1), and location informationassociated with a handler device (e.g. tracking information 136 in FIG.1).

Upon receipt of the first checkpoint data packet, the shippingremittance processor may determine if the tracking location receivedmatches a determined checkpoint, and if so, output a remittanceindication to the shipper remittance account. At which time, a portionof the total delivery remittance for the entire shipment from start 604to end 606 may be allocated to handler remittance account 146.

Should a network connection be unavailable upon arrival at firstcheckpoint 608, tracking information from one or more of the object,transportation vehicle, or handler device, may be stored respectivelyuntil connection can be made. Upon which time, the shipping remittanceprocessor may output the determined remittance indication. By way ofexample, in the embodiment illustrated in FIG. 6, output remittanceindication 150 may indicate to release funds of $200 from the shipperremittance account to the handler remittance account when both thetransportation vehicle and handler device tracking information isverified by shipping remittance processor 102.

This process then repeats for second checkpoint 610, shown as Lincoln,Nebr., and third checkpoint 612, shown as Denver, Colo., and fourthcheckpoint 614, shown as Las Vegas, Nev. Upon arrival at end 608 ofshipping route 602, a final checkpoint data packet is sent to theshipping remittance processor and a final remittance indicationindicating to transmit the remaining portion of the total deliveryremittance balance is output to shipper handler account. In the exampleshown in FIG. 6, a remittance indication is output from the shippingremittance processor for a final remittance of $1,700 to be transferredfrom the shipper remittance account to the handler remittance account.

FIG. 7 depicts an exemplary method 700 for incremental object trackingand progressive remittance, in embodiments. Method 700 is for exampleimplemented within one or more aspects of system 100, of FIG. 1.

In embodiments, method 700 includes operation 702. In operation 702,method 700 may receive shipment details for shipping an object. In oneexample of operation 702, shipping remittance processor 102 receives oneor more of shipper information 106 and shipment information 108.

In embodiments, operation 702 includes sub-operation 704 in which method700 receives checkpoint information. In one example of sub-operation704, shipping remittance processor 102 receives, from shipper 140,desired checkpoints at which object 118 should travel along duringshipment, and such checkpoints are stored in one or more of objectshipment details 206 and object shipping requirements 306.

In embodiments, operation 702 includes sub-operation 706 in which method700 receives remittance information. In one example of sub-operation706, shipping remittance processor 102 receives, from shipper 140,object remittance details 212 and/or checkpoint remittance 312indicating the portion of the total delivery remittance that isallocated for each checkpoint reached during shipment of object 118.

In embodiments, method 700 includes operation 708. In operation 708,method 700 may allocate shipping details with objects being shipped. Inone example of operation 706, shipping remittance processor 102 mayconfigure shipment information 108.

In embodiments, operation 708 includes sub-operation 710 in which method700 receives tracking tag information. In one example of sub-operation710, shipping remittance processor 102 receives, from shipper 140 orhandler 122, tracking tag information of one or more of first trackingtag 128, second tracking tag 130, and handler device 124, and storessuch tracking tag information in shipment information 108 as trackingtag information 304.

In embodiments, operation 708 includes sub-operation 712 in which method700 verifies remittance balance information. In one example ofsub-operation 712, shipping remittance processor 102 accesses, vianetwork 114, shipper remittance account 142 to verify availableremittance to cover the entire remittance from start to end along theconfigured shipping route.

In embodiments, method 700 includes operation 714. In operation 714,method 700 allocates handler information within shipping remittanceprocessor. In one example of operation 714, shipping remittanceprocessor 102 allocates handler information 110 within its associatedmemory.

In embodiments, operation 714 includes sub-operation 716 in which method700 receives handler ID information. In one example of sub-operation716, shipping remittance processor 102 receives, via network 114,handler ID information 402. In embodiments, the handler ID information402 may include authentication information 412 received via handler 122interacting with handler device 124.

In embodiments, operation 714 includes sub-operation 718 in which method700 sends a checkpoint schedule to the handler device. In one example ofsub-operation 718, shipping remittance processor 102 transmits, vianetwork 114, checkpoint schedule 310 to handler device 124.

In embodiments, operation 714 includes sub-operation 720 in which method700 configures handler remittance account. In one example ofsub-operation 720, shipping remittance processor 102 configures handlerremittance account information 404, for example via interaction withhandler 122 via network 114 and handler device 124.

In embodiments, method 700 includes operation 722. In operation 722method 700 receives, periodically, checkpoint data packet includingtracking information of the shipped object. In one example of operation722, shipping remittance processor 102 receives checkpoint data packet116. Checkpoint data packet 116 may be sent according to any thefollowing protocols: periodically regardless of where the object 118 islocated, only when the object 118 reaches a checkpoint, and when firsttracking tag 128, second tracking tag 130 and handler device 124 areable to connect to network 114.

In embodiments, method 700 includes decision 724. In decision 724,method 700 determines if the object has reached a checkpoint. In oneexample of decision 724, shipping remittance processor 102 analyzes theinformation received in checkpoint data packet 116 to against checkpointschedule 310 determine if object 118 has reached a checkpoint. Shippingremittance processor 102 may analyze a timestamp of the trackinginformation to determine if the checkpoint has been reached in a giventime threshold. In another example of decision 724, handler device 124,via tracker 512, compares checkpoint schedule 516 to determine if thehandler 122 has reached a given checkpoint as listed in checkpointschedule 516 stored in memory 502 of handler device 124. If a checkpointhas been reached, method 700 proceeds to operation 726, decision 730, oroperation 732. If a checkpoint has not been reached, method performseither operation 728 or repeats operation 722.

In embodiments, method 700 includes operation 726. In operation 726 thehandler is prompted that a checkpoint has been reached. In one exampleof operation 726, handler device 124 generates prompt 524. In responseto the prompt 524, handler 122 may retrieve one or more trackinginformation 133 from object 118 and tracking information 135 fromtransportation vehicle 126 for relay to shipping remittance processor102 via network 114.

In embodiments, method 700 includes operation 728. In operation 728,method 700 notifies the shipper of a missed checkpoint. In one exampleof operation 728 shipping remittance processor 102 notifies shipper 140when object 118 misses a checkpoint. In embodiments, shipping remittanceprocessor 102 may update checkpoints missed 316 during operation 728.Upon completion of operation 728, method 700 may repeat operation 722.

In embodiments, method 700 includes decision 730. In decision 730,method 700 may authenticate the tracking information of an object. Inone example of decision 730, shipping remittance processor 102 comparesauthentication information 522, received in a checkpoint data packet 116from handler device 124, against authentication information 412. Ifmethod 700 determines that the tracking information is authentic, method700 may proceed to operation 732. Otherwise, method 700 may proceed tooperation 728 and notify the shipper that the received trackinginformation is unauthentic.

In embodiments, method 700 includes operation 732. In operation 732,method 700 outputs a remittance indication indicating to release aportion of the total delivery remittance to a handler remittanceaccount. In one example of operation 732, shipping remittance processor102 outputs remittance indication 150 to shipper remittance account 142indicating to release a portion of the total delivery remittance forshipping object 118 along the shipping route. Upon completion ofoperation 732, method 700 may repeat operation 722 until all checkpointshave been reached.

The systems and methods described above may be used for a variety ofimplementations. For example, the object may be a traveling salesman, atwhich each checkpoint is a stop along the salesman's trip. At eachcheckpoint, the salesman may use his device to indicate he has reached agiven checkpoint. In response, the shipping remittance processor maythen release an output indicating to pay the salesman his per diem andlodging remittance.

As another example, the objects may be transported vehicles. At eachcheckpoint, a tracking tag located on each vehicle being transported,and in embodiments another tracking tag located on the trailer in whichthe transported vehicles are located, may connect with shippingremittance processor, via a network, to verify that the transportedvehicle is at a given checkpoint. In response, the handler (e.g. acourier transporting the transported vehicles) may receive a portion ofthe total delivery remittance for the overall transportation of thevehicle.

As another example, the objects may be freight within a tractor trailer.At each checkpoint, a tracking tag located on a pallet holding theobjects, and in embodiments another tracking tag on the tractor trailer,may connect with shipping remittance processor, via a network, to verifythat the freight is at a given checkpoint. In response, the handler(e.g. a courier transporting the transported vehicles) may receive aportion of the total delivery remittance for the overall transportationof the freight such as gas remittance to reach the next checkpoint.

As yet another example, the objects may be passengers on a passengervehicle operated by a handler. At each checkpoint, a tracking tagassociated with the passenger, such as the passenger's smartphone, maytransmit a checkpoint data packet to the shipping remittance processor.The shipping remittance processor may identify when a passenger exitsthe passenger vehicle based upon the last checkpoint received. At whichtime, the shipping remittance processor may output a remittanceindication indicating to transfer remittance from the passenger'sremittance account to the handler's remittance account.

It should also be appreciated that there may be more than one handler inpossession of the object during the totality of the shipping route. Insuch a case, the handler may modify one or both of the object shippingdetails 308 and object shipping requirements 306 to specify a givenhandler for each checkpoint. The authentication data within eachcheckpoint data packet 116 may then be used to verify that the object iswith the appropriate handler for a given segment of the shipping route.

It should thus be noted that the matter contained in the abovedescription or shown in the accompanying drawings should be interpretedas illustrative and not in a limiting sense. The following claims areintended to cover all generic and specific features described herein, aswell as all statements of the scope of the present method and system,which, as a matter of language, might be said to fall therebetween.

1. A computer-implemented method for incremental object tracking andprogressive remittance, comprising: receiving, at a shipping remittanceprocessor, a checkpoint data packet including (1) location informationdetermined from a tracker system within a handler device, and (2)tracking information of an object during shipment along a shipmentroute; determining, via the shipping remittance processor, that theobject has reached a checkpoint along the shipment route, the checkpointbeing located between a beginning and end of the shipment route, theshipment route including multiple checkpoints for the handler; upondetermining that the object has reached the checkpoint, outputting aremittance indication indicating that a portion of a total deliveryremittance is to be distributed to a handler account.
 2. The method ofclaim 1, the tracking information being relayed by the handler devicefrom a tracking tag located on the object or a shipping vehicle.
 3. Themethod of claim 2, the tracking information including data sent via awireless transmission received by the handler device from the trackingtag located on the object or a shipping vehicle.
 4. The method of claim3, the wireless transmission being one or more of: a RFID scan of thetracking tag by the handler device, and a Bluetooth transmission fromthe tracking tag to the handler device.
 5. The method of claim 1, saidreceiving comprising receipt, via a network, of the checkpoint datapacket as a first communication from a tracking tag located on theobject.
 6. The method of claim 5, said receiving further comprisingreceiving the checkpoint data packet additionally as a secondcommunication from the handler device.
 7. The method of claim 1, saiddetermining including comparing a timestamp of the tracking informationwithin the checkpoint data packet against checkpoint requirements storedin the shipping remittance processor.
 8. The method of claim 1, saidoutputting a remittance indication including sending the remittanceindication to a shipper remittance account.
 9. The method of claim 1,said outputting a remittance indication including sending the remittanceindication to a prepaid resource.
 10. The method of claim 1, furthercomprising authenticating the tracking information.
 11. The method ofclaim 10, said authenticating comprising: receiving, at the shippingremittance processor, an authentication token generated by the handlerdevice.
 12. The method of claim 10, said authenticating comprising:receiving, at the shipping remittance processor, a handler biometricauthentication token received by the handler device, the handlerbiometric authentication token including one or more of: a handlerfingerprint scan, a handler facial scan, and a handler retinal scan. 13.The method of claim 1, the object being a passenger in a passengervehicle, the checkpoint data packet being received via a transmissionfrom a mobile device of the passenger.
 14. A system for incrementalobject tracking and progressive remittance, comprising: a memory storinga checkpoint schedule defining checkpoints for an object traveling alonga shipping route; a shipping remittance processor adapted to executenon-transitory computer readable instructions to: receive a checkpointdata packet including (1) location information determined from a trackersystem within a handler device, and (2) tracking information of theobject during shipment along the shipping route, the shipping routeincluding multiple checkpoints for the handler; compare the trackinginformation with the checkpoint schedule to determine if the object hasreached one of the checkpoints, and output a remittance indicationindicating that a portion of a total delivery remittance is to bedistributed to a handler remittance account.
 15. The system of claim 14,further comprising a communication manager in communication with theshipping remittance processor for receiving the checkpoint data packetvia a wireless transmission.
 16. A handler device for incremental objecttracking and progressive remittance, comprising: a memory storing acheckpoint schedule identifying shipping checkpoints along a shippingroute for shipping an object, the shipping route including multiplecheckpoints for the handler; a tracker for determining a real-timegeographical location of the handler device; a handler processor incommunication with the memory and tracker, the handler processorconfigured to analyze the checkpoint schedule and output, via an outputdevice, a prompt to a user to obtain authentication information inresponse to the real-time geographical location matching one of thecheckpoints; an input interface configured to receive the authenticationinformation.
 17. The handler device of claim 16, further comprising atransmitter for transmitting a checkpoint data packet including theauthentication information to a shipping remittance processor.
 18. Thehandler device of claim 16, the input interface including a wirelessscanner for receiving location information of an object via one or moreof a RFID scan of a tracking tag located on the object, and a Bluetoothtransmission from the tracking tag located on the object.
 19. Thehandler device of claim 16, the input interface including a biometricscanner; the authentication information including one or more of: ahandler fingerprint scan, a handler retinal scan, and a handler facialscan received via the biometric scanner.
 20. The handler device of claim16, further comprising a receiver for receiving a remittance data packetindicating remittance has been placed in a handler remittance account.